Skip to content

Conversation

fandreuz
Copy link
Contributor

@fandreuz fandreuz commented Sep 29, 2025

The test checks whether writing to a read-only directory throws a IOException. This test is not applicable when the user running the test is root. Thus, I propose to skip it.

I converted the class to several JUnit tests, so we can use @DisabledIf.


Progress

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue

Issue

  • JDK-8368846: java/io/File/createTempFile/TargetDirectory fails when run by root user (Enhancement - P4)

Reviewers

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/27542/head:pull/27542
$ git checkout pull/27542

Update a local copy of the PR:
$ git checkout pull/27542
$ git pull https://git.openjdk.org/jdk.git pull/27542/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 27542

View PR using the GUI difftool:
$ git pr show -t 27542

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/27542.diff

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Sep 29, 2025

👋 Welcome back fandreuzzi! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk
Copy link

openjdk bot commented Sep 29, 2025

@fandreuz This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8368846: java/io/File/createTempFile/TargetDirectory fails when run by root user

Reviewed-by: bpb

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 24 new commits pushed to the master branch:

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@bplb) but any other Committer may sponsor as well.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

@openjdk
Copy link

openjdk bot commented Sep 29, 2025

@fandreuz The following label will be automatically applied to this pull request:

  • core-libs

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

@openjdk openjdk bot added the rfr Pull request is ready for review label Sep 29, 2025
@mlbridge
Copy link

mlbridge bot commented Sep 29, 2025

Webrevs

* @bug 4847239
* @summary Verify directory parameter behavior in File.createTempFile(String,String,File)
* @library /test/lib
* @run junit/othervm TargetDirectory
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is othervm needed here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not really, fixed


class TargetDirectory {

@TempDir
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In my testing I saw this output for each of the four sub-tests:

INFO: Skipping cleanup of temp dir [...] for field TargetDirectory.tempDir due to CleanupMode.NEVER.

Should this have CleanupMode.ALWAYS? In the old version of the test there were explcit calls to File.delete.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed, thanks

public static void main(String[] args) throws Exception {
// Target directory exists and is writable
Path dir = Path.of("target");
import static org.junit.jupiter.api.Assertions.*;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you can dispense with the wild card at line 50 by doing:

import static org.junit.jupiter.api.Assertions.assertThrows;
import static org.junit.jupiter.api.Assertions.assertTrue;

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed

}

@Test
@DisabledIf("jdk.test.lib.Platform#isRoot")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will silently skip the test.
Jtreg has a feature for keeping track of Skipped tests and reporting they were skipped.
Throwing SkippedException would enable that reporting.
Take a look at a similar test: test/jdk/java/io/File/SetAccess.java

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will silently skip the test.

I ran the test as root and as my normal user. For the normal user one gets

STARTED    TargetDirectory::testReadOnlyDirectory 'testReadOnlyDirectory()'

whereas for root

SKIPPED    TargetDirectory::testReadOnlyDirectory 'testReadOnlyDirectory()' @DisabledIf("jdk.test.lib.Platform#isRoot") evaluated to true

which looked okay to me.

Copy link
Member

@bplb bplb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good now.

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Oct 10, 2025
@fandreuz
Copy link
Contributor Author

Thanks for the review @RogerRiggs and @bplb.

@fandreuz
Copy link
Contributor Author

/integrate

@openjdk openjdk bot added the sponsor Pull request is ready to be sponsored label Oct 10, 2025
@openjdk
Copy link

openjdk bot commented Oct 10, 2025

@fandreuz
Your change (at version 8b82864) is now ready to be sponsored by a Committer.

@bplb
Copy link
Member

bplb commented Oct 10, 2025

/sponsor

@openjdk
Copy link

openjdk bot commented Oct 10, 2025

Going to push as commit fc49a1b.
Since your change was applied there have been 31 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Oct 10, 2025
@openjdk openjdk bot closed this Oct 10, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review sponsor Pull request is ready to be sponsored labels Oct 10, 2025
@openjdk
Copy link

openjdk bot commented Oct 10, 2025

@bplb @fandreuz Pushed as commit fc49a1b.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

core-libs [email protected] integrated Pull request has been integrated

Development

Successfully merging this pull request may close these issues.

3 participants